Tracing Software Requirements Artifacts
نویسندگان
چکیده
The support for traceability between requirement specifications has been recognised as an important task in the development life-cycle of software systems. In this paper we present an approach for automatic generation and maintenance of bi-directional traceability relations between commercial and functional requirements expressed in natural language, and requirement object models. The generation of traceability relations is based on two types of traceability rules: requirements-to-object-model rules and inter-requirements rules. Our approach support three different types of traceability relations namely overlaps, realises, and requires. The requirement artefacts and traceability rules are described in XML. A prototype tool has been developed to demonstrate our approach, and has been used in a series of experiments that we have conducted to evaluate it. The results of these experiments
منابع مشابه
Resolving Semantic Heterogeneity in Multiperspective Requirements Traceability Using Ontology Matching
In large-scaled software development projects, different stakeholders may deal with different pieces of software requirements depending on their perspectives or perceptions of their shared problems. Each of the users may define his/her requirements from his/her own point of view using different terminologies. System analysts may express or model the artifacts of the system by using different re...
متن کاملAn Initial Tracing Activity Model to Balance Tracing Agility and Formalism Requirements Tracing Strategies for Change Impact Analysis and Re-Testing
Software customers want both sufficient product quality and agile response to requirements changes. Formal software requirements tracing helps to systematically determine the impact of changes and keep track of development artifacts that need to be re-tested when requirements change. However, full tracing of all requirements on the most detailed level can be very expensive and time consuming. I...
متن کاملModeling of Requirements Tracing
Software customers want both sufficient product quality and agile response to requirements changes. Formal software requirements tracing helps to systematically determine the impact of changes and to keep track of development artifacts that need to be re-tested when requirements change. However, full tracing of all requirements on the most detailed level can be very expensive and time consuming...
متن کاملRequirements Tracing Strategies for Change Impact Analysis and Re-Testing An Initial Tracing Activity Model and Industry Feasibility Study
Software requirements tracing is a systematic approach to keep track of development artifacts that need to be re-tested when requirements change. An important question is how much investment into tracing seems reasonable in an environment. This paper proposes an initial tracing activity model for trace generation and usage to help determine tracing efforts and support test managers in tailoring...
متن کاملTracing requirements and source code during software development
Traceability links between requirements and source code are often created after development. This reduces the possibilities for developers to use these traceability links during the development process. Additionally, existing approaches applied after development do not consider artifacts from project management, which are used for planning and organizing a project. These artifacts can serve as ...
متن کاملSemTrace: Semantic Requirements Tracing Using Explicit Requirement Knowledge
In the software engineering (SE) domain the EU challenge on semantic systems and services motivates better support of knowledge creation as well as better access of SE stakeholders to the knowledge they need to perform their activities. Application Lifecycle Management (ALM) is the coordination of development lifecycle activities by process automation, management of relationships between artifa...
متن کامل